VMware vSphere 6.7 Perfcharts Tomcat Security Technical Implementation Guide

Overview

Version	Date	Finding Count (31)			Downloads
1	2022-01-03 2021-04-15 2021-04-15	CAT I (High): 0	CAT II (Med): 31	CAT III (Low): 0	Excel	JSON	XML

STIG Description
This Security Technical Implementation Guide is published as a tool to improve the security of Department of Defense (DoD) information systems. The requirements are derived from the National Institute of Standards and Technology (NIST) 800-53 and related documents. Comments or proposed revisions to this document should be sent via email to the following address: disa.stig_spt@mail.mil.

Available Profiles

Classified	Public	Sensitive
I - Mission Critical Classified	I - Mission Critical Public	I - Mission Critical Sensitive	II - Mission Support Classified	II - Mission Support Public	II - Mission Support Sensitive	III - Administrative Classified	III - Administrative Public	III - Administrative Sensitive

Findings (MAC III - Administrative Sensitive)

Finding ID	Severity	Title	Description
V-239430	Medium	Performance Charts must disable the shutdown port.	An attacker has at least two reasons to stop a web server. The first is to cause a denial of service, and the second is to put in place changes the attacker made to the web server configuration....
V-239431	Medium	Performance Charts must set the secure flag for cookies.	The secure flag is an option that can be set by the application server when sending a new cookie to the user within an HTTP Response. The purpose of the secure flag is to prevent cookies from...
V-239432	Medium	Performance Charts must be configured to limit access to internal packages.	The "package.access" entry in the "catalina.properties" file implements access control at the package level. When this is properly configured, a Security Exception will be reported if an errant or...
V-239409	Medium	Performance Charts application files must be verified for their integrity.	Verifying that the Security Token Service application code is unchanged from its shipping state is essential for file validation and nonrepudiation of Performance Charts. There is no reason that...
V-239408	Medium	Performance Charts log files must only be modifiable by privileged users.	Log data is essential in the investigation of events. The accuracy of the information is always pertinent. One of the first steps an attacker will undertake is the modification or deletion of log...
V-239405	Medium	Performance Charts must protect cookies from cross-site scripting (XSS).	Cookies are a common way to save session state over the HTTP(S) protocol. If an attacker can compromise session data stored in a cookie, they are better able to launch an attack against the server...
V-239404	Medium	Performance Charts must limit the maximum size of a POST request.	The "maxPostSize" value is the maximum size in bytes of the POST that will be handled by the container FORM URL parameter parsing. Limiting its size will reduce exposure to a denial-of-service...
V-239407	Medium	Performance Charts must generate log records for system startup and shutdown.	Logging must be started as soon as possible when a service starts and when a service is stopped. Many forms of suspicious actions can be detected by analyzing logs for unexpected service starts...
V-239406	Medium	Performance Charts must record user access in a format that enables monitoring of remote access.	Remote access can be exploited by an attacker to compromise the server. By recording all remote access activities, it will be possible to determine the attacker's location, intent, and degree of...
V-239403	Medium	Performance Charts must limit the number of concurrent connections permitted.	Resource exhaustion can occur when an unlimited number of concurrent requests are allowed on a website, facilitating a denial-of-service attack. Unless the number of requests is controlled, the...
V-239402	Medium	Performance Charts must limit the amount of time that each TCP connection is kept alive.	Denial of service (DoS) is one threat against web servers. Many DoS attacks attempt to consume web server resources in such a way that no more resources are available to satisfy legitimate...
V-239427	Medium	Performance Charts must properly configure log sizes and rotation.	To ensure that the logging mechanism used by the web server has sufficient storage capacity in which to write the logs, the logging mechanism must be able to allocate log record storage capacity....
V-239426	Medium	Performance Charts must have the debug option turned off.	Information needed by an attacker to begin looking for possible vulnerabilities in a web server includes any information about the web server and plug-ins or modules being used. When debugging or...
V-239425	Medium	Performance Charts must not enable support for TRACE requests.	"Trace" is a technique for a user to request internal information about Tomcat. This is useful during product development but should not be enabled in production. Allowing an attacker to conduct...
V-239424	Medium	Performance Charts must be configured to show error pages with minimal information.	Web servers will often display error messages to client users, including enough information to aid in the debugging of the error. The information given back in error messages may display the web...
V-239423	Medium	Performance Charts must not show directory listings.	Enumeration techniques, such as URL parameter manipulation, rely on being able to obtain information about the web server's directory structure by locating directories without default pages. In...
V-239422	Medium	Performance Charts must set the welcome-file node to a default web page.	Enumeration techniques, such as URL parameter manipulation, rely on being able to obtain information about the web server's directory structure by locating directories without default pages. In...
V-239421	Medium	Performance Charts must use the "setCharacterEncodingFilter" filter.	Invalid user input occurs when a user inserts data or characters into a hosted application's data entry field and the hosted application is unprepared to process that data. This results in...
V-239420	Medium	Performance Charts must set "URIEncoding" to UTF-8.	Invalid user input occurs when a user inserts data or characters into a hosted application's data entry field and the hosted application is unprepared to process that data. This results in...
V-239429	Medium	Performance Charts must be configured with the appropriate ports.	Web servers provide numerous processes, features, and functionalities that use TCP/IP ports. Some of these processes may be deemed unnecessary or too unsecure to run on a production system. The...
V-239428	Medium	Rsyslog must be configured to monitor and ship Performance Charts log files.	Performance Charts produces a handful of logs that must be offloaded from the originating system. This information can then be used for diagnostic purposes, forensics purposes, or other purposes...
V-239418	Medium	Performance Charts must fail to a known safe state if system initialization fails, shutdown fails, or aborts fail.	Determining a safe state for failure and weighing that against a potential denial of service for users depends on what type of application the web server is hosting. For Performance Charts, it is...
V-239419	Medium	Performance Charts must limit the number of allowed connections.	Limiting the number of established connections to Performance Charts is a basic denial-of-service protection. Servers where the limit is too high or unlimited can potentially run out of system...
V-239412	Medium	Performance Charts must have Multipurpose Internet Mail Extensions (MIME) that invoke OS shell programs disabled.	MIME mappings tell the Performance Charts what type of program various file types and extensions are and what external utilities or programs are needed to execute the file type. By ensuring that...
V-239413	Medium	Performance Charts must have mappings set for Java servlet pages.	Resource mapping is the process of tying a particular file type to a process in the web server that can serve that type of file to a requesting client and to identify which file types are not to...
V-239410	Medium	Performance Charts must only run one web app.	VMware ships Performance Charts on the VCSA with one web app. Any other path is potentially malicious and must be removed.
V-239411	Medium	Performance Charts must not be configured with unsupported realms.	Performance Charts performs user authentication at the application level and not through Tomcat. Depending on the VCSA version, Performance Charts may come configured with a "UserDatabaseRealm"....
V-239416	Medium	Performance Charts must not have any symbolic links in the web content directory tree.	A web server is designed to deliver content and execute scripts or applications on the request of a client or user. Containing user requests to files in the directory tree of the hosted web...
V-239417	Medium	Performance Charts directory tree must have permissions in an "out-of-the box" state.	Accounts on a web server are to be kept to a minimum. Only administrators, web managers, developers, auditors, and web authors require accounts on the machine hosting the web server. The resources...
V-239414	Medium	Performance Charts must not have the Web Distributed Authoring (WebDAV) servlet installed.	WebDAV is an extension to the HTTP protocol that, when developed, was meant to allow users to create, change, and move documents on a server, typically a web server or web share. WebDAV is not...
V-239415	Medium	Performance Charts must be configured with memory leak protection.	The Java Runtime environment can cause a memory leak or lock files under certain conditions. Without memory leak protection, Performance Chart can continue to consume system resources that will...